3.3. Vendor 3

The main value of the interop to this vendor was being in the same room as some of the other developers. This was invaluable for learning about how to configure better logging and also in diagnosing issues in both clients and our server.

Their CalDAV Schedule support did not work at all with one of the clients and they spent a lot of time diagnosing issues with that and fixing them. They didn’t support principal-property-search reports, for instance, which was a major blocker.

When updating a calendar entry, the server was using the HTTP status code of Created, which is incorrect for an update. The other vendor application was unhappy with this status code. It was creating meetings without an ORGANIZER at one point and this resulted in the server creating corrupt ORGANIZER fields in subsequent accesses.

Initial testing yet another vendor showed that the test version of that vendor’s application was not recognizing our Meeting Requests at all. This was subsequently fixed by them.

A lack of iMip support prevented IOP testing with two of the server applications at the event.